Skip to content

IV-107 Restore compact component gallery - #10

Draft
heyinterspace wants to merge 6 commits into
stagingfrom
agent/iv-107-scientific-motion-components
Draft

IV-107 Restore compact component gallery#10
heyinterspace wants to merge 6 commits into
stagingfrom
agent/iv-107-scientific-motion-components

Conversation

@heyinterspace

@heyinterspace heyinterspace commented Aug 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • restore intrinsic-height, two-column masonry packing for component specimens
  • give Category filters raised neutral-gray button surfaces
  • keep Type filters smaller and flatter so the two axes remain distinct
  • replace the stark white secondary nav utility with a neutral-gray surface
  • protect the isolated staging environment with server-enforced Clerk authentication and an exact email allowlist
  • mark the deployed specimen visibly as Staging without changing production behavior

Validation

  • workspace and artifact TypeScript checks
  • production Vite and Express builds
  • registry drift and shadcn schema validation (89 items)
  • adopter validation (11 projects)
  • git diff check
  • fail-closed staging configuration check
  • production-mode localhost health and site smoke checks
  • GitHub Actions CI passed
  • Railway staging deployment passed and serves commit 9407dd2
  • anonymous staging HTML redirects to Clerk
  • anonymous staging API returns 401
  • /api/health remains public and returns 200
  • Railway provider URL redirects to the canonical staging domain
  • noindex/private-cache headers verified
  • production structured.glass remains public and unchanged

Staging

  • https://staging.structured.glass
  • Railway environment: staging
  • source: agent/iv-107-scientific-motion-components
  • deployed commit: 9407dd2
  • Wait for CI: enabled and verified
  • Clerk application: Structured · Staging (isolated, development instance, invite-only)
  • samir@interspace.ventures: invitation sent; server allowlist active

Release state

  • feature branch, draft PR, and isolated staging environment only
  • production remains unchanged at 09900ba
  • merge and production deployment remain separate approval gates

Prompt: Keep component specimens in a compact multi-column layout, let masonry absorb vertical gaps, distinguish category and type filters, and use neutral gray for the non-primary nav button.
@railway-app
railway-app Bot temporarily deployed to Structured / staging August 22, 2026 13:08 Inactive
Prompt: Can you have staging on the live domain? You can add clerk auth for access and make sure samir@interspace.ventures has access. Should be staging.structured.glass.
@railway-app
railway-app Bot temporarily deployed to Structured / staging August 22, 2026 13:36 Inactive
Prompt: Audit the mobile design, replace icon-only navigation with a clear hamburger menu, left-align mobile hierarchy, fix broken narrow-width components, remove ghost and link from the button specimen, replace real-app placeholder copy with a coherent fictional science-fiction theme, and advise whether Structured should be surfaced through Exobase.
@railway-app
railway-app Bot temporarily deployed to Structured / staging August 23, 2026 02:02 Inactive
Prompt: why do the clerk sign ins get redirected to clerk auth urls though? I want them to be embedded on our site with our domains etc. this should be true for every Exobase app. Shouldn’t be a random url
@railway-app
railway-app Bot temporarily deployed to Structured / staging August 24, 2026 02:43 Inactive
Prompt: Clerk sign-ins and invitations should be embedded on each application domain rather than starting on a random Clerk-hosted URL.
@railway-app
railway-app Bot temporarily deployed to Structured / staging August 24, 2026 02:55 Inactive
Prompt: Add a subtle background grid, make gallery Category and Type selectors visually distinct from the background, and use one, two, or three gallery columns for mobile, laptop, and wide screens.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant